All translators are the same to a certain extent: they must contain the getTranslatorInfo() and translateMarkup() functions, and they must reside in the Configuration/Translators folder. They differ, however, in the kind of code that they insert into the user's document, and in how that code must be inspected.
|
To translate small pieces of server markup that determine attribute values or that conditionally add attributes to a standard HTML tag, write an attribute translator. Standard HTML tags that contain translated attributes can be inspected with the property inspectors that are built into Dreamweaver. It is not necessary to write a custom property inspector. See Adding a translated attribute to a tag. |
|
To translate an entire tag (for example, a server-side include) or a block of code (for example, JavaScript, Cold Fusion, PHP, or other scripting), write a block/tag translator. The code generated by a block/tag translator cannot be inspected with the property inspectors that are built into Dreamweaver. You must write a custom inspector for the translated content if you want users to be able to change the properties of the original code. See Locking translated tags or blocks of code. |